home *** CD-ROM | disk | FTP | other *** search
- Path: newsbf02.news.aol.com!not-for-mail
- From: champalber@aol.com (Champalber)
- Newsgroups: comp.lang.c++
- Subject: How to shrink your Windows program by %80!
- Date: 2 Mar 1996 20:57:01 -0500
- Organization: America Online, Inc. (1-800-827-6364)
- Sender: root@newsbf02.news.aol.com
- Message-ID: <4hau9d$m3@newsbf02.news.aol.com>
- NNTP-Posting-Host: newsbf02.mail.aol.com
- X-Newsreader: AOL Offline Reader
-
- How is that possable? Convert it to Pascal.
-
- Does anybody use Turbo Pascal (TP) for Windows? Having used only
- BorlandC++ (BC) for Windows for the past few years, I was amazed to see
- how much faster TP compiled and how much smaller the resulting code was.
- If you have these two products try out a simple experiment: Write the
- "hello world. program for Windows" with each compiler, then look and see.
-
- When I compiled with TP I thought that the compilation had stopped on an
- error, but no, it was just _very_ fast. In my particular case I wrote a
- very simple program to write a few lines of text in a window; a simple
- task that I wanted to spend as little time writing as possible, so I used
- OWL for BC, and the equivilent for TP.
-
- The size comparison: BC - 90k, TP - 14k!
- The two programs do _exactly_ the same thing.
-
- What is surprising is that both compilers are written by Borland, and the
- Windows stuff in Pascal is very similar to the C++ version - same Windows
- functions, same sequence of functions.
-
- Why does one compiler seem to be so much more efficient than the other?
- There is always the argument that "you get all the C++ goodies", but using
- TP you can do just about everything that you can do in BC, with seamingly
- increadable savings on final exe size.
-
- Richard Champalbert
- champalber@aol.com
-
- Champalbert
- champlaber@aol.com
-